Release 10.1A: OpenEdge Application Server:
Administration

WSA as a JSE Web application

To configure a WSA, it is also necessary to understand the architecture of the WSA as a JSE Web application. The WSA Web application consists of a set of directories and files. Figure 5–2 shows the directory structure.

. . . /WSA-web-application-directory        [ optional static html pages ]        .        .        .        WEB-INF/               web.xml ( WSA Web application descriptor file )               lib/                      wsa.jar                      soap.jar                      [ any additional WSA Web application jar files ]                      .                      .                      .               classes/                      [ optional Java .class files ]                      .                      .                      .

Figure 5–2: Directory structure of the WSA as a JSE Web application

The WSA Web application consists of a subdirectory named WEB-INF (the name is case sensitive) that contains the Web application descriptor file (web.xml) and two subdirectories for holding Java class files and Java jar files. The WSA Web application does not contain any class files, but does include several jar files. These form a single Web application that can contain one or more WSA instances. A JSE can contain multiple WSA Web applications, and each Web application can contains multiple WSA instances.

Configuring a WSA Web application involves editing its web.xml file, an XML-based file that must conform to the JSE version’s document type definition (DTD) published by Sun Microsystems, Inc. You might have to manually edit web.xml to set WSA instance security or to add a WSA instance to the WSA Web application. For a full description of the web.xml file, see Sun’s JSE specifications.